-
Notifications
You must be signed in to change notification settings - Fork 264
chore: drop status go ethereum fork #6961
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Jenkins BuildsClick to see older builds (94)
|
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## develop #6961 +/- ##
===========================================
+ Coverage 55.44% 59.39% +3.94%
===========================================
Files 833 823 -10
Lines 120101 116697 -3404
===========================================
+ Hits 66595 69315 +2720
+ Misses 46535 40274 -6261
- Partials 6971 7108 +137
Flags with carried forward coverage won't be shown. Click here to find out more.
|
c020188 to
bd4386a
Compare
64516e8 to
391a815
Compare
bd4386a to
d064ce0
Compare
2f71258 to
79d2d46
Compare
c89a9ca to
c7fcae5
Compare
79d2d46 to
17f7c1a
Compare
c7fcae5 to
ba10eaa
Compare
|
I've checked once again the status-go/services/ext/service.go Line 354 in 7c3969b
That verifies transactions from status-go/protocol/persistence.go Line 1024 in e221047
When do we save to
|
| func (db sqlitePersistence) SaveTransactionToValidate(transaction *TransactionToValidate) error { | |
| compressedKey := crypto.CompressPubkey(transaction.From) | |
| _, err := db.db.Exec(`INSERT INTO messenger_transactions_to_validate( |
... when we receive ApplicationMetadataMessage_SEND_TRANSACTION message.
When is SEND_TRANSACTION used?
And this can be triggered by one of the 2:

-
AcceptRequestTransactionis an API method.
This goes through a few levels of Nim and appears in QML: AcceptRequestTransaction
... and NOT USED. -
SendTransactionis also an API method.
And this doesn't even appear being used in Nim, so... NOT USED.
So I guess this can be dropped. I'll take care of it
ba10eaa to
6b24327
Compare
17f7c1a to
3e24920
Compare
6b24327 to
6637db7
Compare
c7a8bfa to
0ec75ce
Compare
a1c4195 to
c9ab1fe
Compare
0ec75ce to
5029829
Compare
c7131e1 to
a54b7fb
Compare
* chore: upgrade go-waku and go-discover * chore: make vendor * feat: go-waku v0.10.0
a54b7fb to
241278c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
changes to go.mod and go.sum look good from devops POV.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🙌 🙌 🙌

status-desktop PR for testing: status-im/status-desktop#18960
Blocked by:
go-wakuwith upstreamgo-ethereum#6978This PR drops use of our infamous go-ethereum fork (https://github.com/status-im/go-ethereum).
status-go will after this be using the original one (https://github.com/ethereum/go-ethereum).
Much work was done by many folks to get status-go to a state where it stops relying on our changes on top of the go-ethereum version we used as base: ethereum/go-ethereum@master...status-im:go-ethereum:release/v1.10.25-status
Much additional work was done to adapt to the changes between geth v1.10.25 and v1.16.3
This PR includes the final changes missing which mostly cannot be introduced without changing the geth version at the same time.